Cream of the Crop 12

home *** CD-ROM | disk | FTP | other *** search

/ Cream of the Crop 12 / Cream of the Crop 12 (Part II) / Cream of the Crop 12 (Part II).iso / BBS / VFY_39.ZIP / VERIFY!.DOC < prev next >

Wrap

Text File | 1996-02-11 | 55.4 KB | 1,280 lines

************************************************************** * * * VERIFY!.EXE v3.9 Copyright (c) 1991-96 * * * * Sagerquist Micro Engineering * * * * 1414 W. Kerrick Street * * Lancaster, Ca. 93534 * * Data (805) 723-6908 * * * * Internet * * E-Mail: zs@qnet.com * * WWW: http://www.av.qnet.com/~zs/ * * * ************************************************************** DESCRIPTION ----------- VERIFY! is a program designed to verify a BBS caller. When invoked, VERIFY! will ask for specific information from the caller, hang up, return the call, and ask for the same data for verification. If the information matches, the caller is verified. ERRORLEVELs are returned to the calling batch file which will allow the sysop to make the necessary adjustments to the BBS as appropriate. A log file is kept and maintains the caller's name and phone number for future reference. SYNTAX ------ VERIFY! [/B:...] [/D:...] [/L:...] [/H:...] [/REQUIRED:...] /B:... BBS switch. Choose from the list under SUPPORTED BBS's. /D:... Directory (no file name) where the BBS's caller information file is located. If this switch is not used, VERIFY! will look for this file in the current directory only. /L:... Optional log file path and name. If you want VERIFY! to log its operations in your BBS log file, use this switch to define the full drive:\path\filename.ext. If this switch is not used, the default file VERIFY!.LOG will be created and updated. /NODE: Optional node number. If using nonstandard IRQs on a multinode system, and the node number is not defined in the BBSs drop file (Remote Access's DORINFO1.DEF and CHAIN.TXT), use this command line switch. Default is 1 (NODE 1) unless overridden by the BBS drop file or this switch. /H:... YES/NO/NORMAL Optional hangup control, default: NORMAL. After verification, you may either force a disconnect, or leave the caller online. Without this switch, (or with the "NORMAL" command), local calls stay online, toll and long distance disconnect after verification. /REQUIRED:... YES/NO Optional, default: NO. Disallows the caller from exiting the program without completing verification. Keyboard timeout hangs up the line. EXAMPLES -------- VERIFY! /B:MH1 VERIFY! /B:TRIBBS /D:C:\TRIBBS VERIFY! /B:WILDCAT /D:C:\WC30\WCWORK /L:C:\WC30\WCWORK\WC.LOG VERIFY! /B:WILDCAT /D:C:\WC40\WCWORK\NODE%WCNODEID% /L:C:\WC40\WCWORK\WC.LOG VERIFY! /B:SPITFIRE /D:C:\SPITFIRE /H:YES /REQUIRED:YES Note: # is Node Number SUPPORTED BBS's Switch: Caller Info File: ---------------------------------------------------------- Auntie: AUNTIE AUNTIE.SYS LoraBBS: LORABBSxx LORAINFO.Txx MegaHost: MH# MEGAHST#.DEF PcBoard: PCBOARD DOOR.SYS ProBoard: PROBOARD DORINFO#.DEF QuickBBS: QBBS# DORINFO#.DEF RBBS: RBBS# DORINFO#.DEF Remote Access: RA DORINFO1.DEF Renegade: RENEGADE# DORINFO#.DEF RoboBoard: ROBOFX# DORINFO#.DEF Spitfire: SPITFIRE SFDOORS.DAT Telegard: TELEGARD CHAIN.TXT TGP: TGP CHAIN.TXT TRIBBS: TRIBBS TRIBBS.SYS Ultra BBS: UBBS DOOR.SYS Virtual BBS/NET: VBBS CHAIN.TXT Wildcat: WILDCAT DOOR.SYS WWIV: WWIV CHAIN.TXT FILES IN THIS ZIP PACKAGE ------------------------- VERIFY! EXE <----------- Executable program. VERIFY! DOC <----------- Document for VERIFY!.EXE - this file. SETUP EXE <----------- Set up program, sets sysop's variables. SETUP DOC <----------- Document for SETUP.EXE. TRAPDOOR BAT <----------- Example of a Trap Door batch file. TEST BAT <----------- Batch file for initial testing. REGISTER FRM <----------- Fill-Out form for registration. TRIBBS SYS <----------- Sample TriBBS drop file for testing. NSTD IRQ <----------- Nonstandard IRQ definitions (if any). VERIFY! DAT <----------- Created or adjusted by SETUP.EXE, holds the reg number, modem strings, phone numbers for screening, etc. FIX_DAT EXE <----------- Adjusts the file VERIFY!.DAT. Works only for upgrading from v2.8 and above. FILE_ID DIZ <----------- Description for a BBS file list. 4-TRIBBS ZIP <----------- Support programs for TriBBS BBS system. 4-WC40 ZIP <----------- Support program for Wildcat v4 BBS system. 4SPTFIRE ZIP <----------- Support program for Spitfire BBS system. OPENSCR ASC/ANS <----------- Output files: Opening screen. FOUND_EM ASC/ANS <----------- Output files: If caller is already verified. REQUIRED ASC/ANS <----------- Output files: If /REQUIRED:YES switch is used. INSTRUCT ASC/ANS <----------- Output files: User's instructions. LCL_TIME ASC/ANS <----------- Output files: If local call back is outside defined times. LD_TIME ASC/ANS <----------- Output files: If long distance call back is outside defined times. DUPENUM ASC/ANS <----------- Output files: If call back number is a duplicate of other caller. BADPHNUM ASC/ANS <----------- Output files: If call back number cannot be called. SABOTAGE ASC/ANS <----------- Output files: If call back number matches those defined as UNAUTHOR- IZED like 911. CALLING ASC/ANS <----------- Output files: Everything OK, call will be placed. RECONECT ASC/ANS <----------- Output files: On reconnection after call back. TRYAGAIN ASC/ANS <----------- Output files: If the caller types the info wrong after call back. SUCCESS ASC/ANS <----------- Output files: On successful verification. FAILURE ASC/ANS <----------- Output files: On failed call back. LDHANGUP ASC/ANS <----------- Output files: On successful call back and if long distance, just prior to hang up. HANGUP ASC/ANS <----------- Output files: On successful call back and if a disconnection is forced. OTHER FILES ----------- VERIFY!.LST <----------- Created by VERIFY!, contains a list of verified callers and their phone numbers. VERIFY! checks this list for duplicate names and phone numbers, and to ensure that a caller isn't verified more than once. VERIFY!.LOG <----------- Default log file created by VERIFY!.EXE. Logs the caller's actions, for sysop's information if the /L: switch is not used. SETUP ----- SHARE.EXE must be loaded since file locking takes place when writing to the log and list files. SETUP.EXE must be run prior to going on line. All data, modem strings, authorized area codes and prefixes, long distance call back times, registration number, etc., must be edited with this program. SETUP.DOC explains the setup operation in better detail. Your calling batch file must be edited, or renamed. TRAPDOOR.BAT is supplied to help you start. VERIFY!.DAT ADJUSTMENT ON UPGRADE --------------------------------- If you've been using VERIFY!.EXE v2.8 or above, FIX_DAT.EXE will be run automatically to adjust the binary file VERIFY!.DAT for use with the current version of VERIFY!.EXE. The extra space in the new data structure will be blank, but this ensures that VERIFY! will operate cleanly if you forget to run SETUP.EXE during the upgrade. Run SETUP.EXE to ensure that all data is in its proper places. The program FIX_DAT.EXE can be run alone, but is called automatically by VERIFY!.EXE and SETUP.EXE if the file VERIFY!.DAT is not correct for this release. FIX_DAT.EXE must reside in the same directory as VERIFY!.EXE, SETUP.EXE and VERIFY!.DAT. If upgrading from a release prior to v2.8, VERIFY!.DAT is renamed to VFY!DAT.OLD and all data must be reentered manually. REGISTRATION AND SUPPORT ------------------------ This is important! Until VERIFY! is registered with the programmer, one very important feature is inhibited: The call screening. After the sysop name and registration number is entered via SETUP.EXE, you will be able to screen out toll and long distance calls, and designate the time of day to make these calls. Your number will be mailed upon receipt of the registration fee. Without this feature, (BEFORE REGISTRATION), any request to call back verify is granted! If your BBS is in Los Angeles, CA, and a caller from New York, NY requests to be verified, YOUR PHONE BILL WILL REFLECT THIS EXPENSIVE CALL! With this feature (after registration), you can adjust VERIFY! to call back verify ONLY local calls, or long distance numbers ONLY within the area code(s) you designate. Also, prior to registration, only three (three digit) numbers of the "Unauthorized Numbers" are screened out. Be sure that the numbers "911 900 976" are the first three listed for safety. The entire line is active after registration. This is a user supported product. VERIFY! represents many hours of work. This software is Shareware, not free or public domain. You are granted a 30 day limited license to evaluate this program, after which you must either register the product, or discontinue its use. If you choose to register this program, please make out a check or money order for $15.00 payable to: Sagerquist Micro Engineering 1414 W. Kerrick St. Lancaster, CA 93534-2225 California residents add 8.25% Sales Tax of $1.24, total: $16.24. Your registration number will be mailed on receipt of your payment. It is recommended that you register this program promptly, as the toll charges for long distance call backs have the potential to far exceed the $15.00 requested! Payment is a one time investment which allows you all further revisions at no extra expense. The registration number generator has changed starting with v3.5. If you're a registered user of VERIFY!, please contact Sagerquist Micro Engineering for your free registration number upgrade. Please distribute this program, i.e. place it in your communications program download area for others to evaluate and use. Your comments on this program are gladly accepted (requested, actually) at the number below and through the Internet. Please use the BBS or the Internet as our communication vehicle. I will gladly respond to all comments through these means. The Sagerquist Micro Engineering Support BBS Carl Sagerquist - Programmer/Sysop 300-28800 BAUD 24 Hours (805) 723-6908 http://www.av.qnet.com/~zs/ zs@qnet.com Upgrading a caller's security level while they are online is the most attractive part of this program. MEGAHOST includes an API program to perform this task. Other BBS's may or may not do the same. Included in this package are four ZIP'ed files with support for LoraBBS, TRIBBS, Wildcat v4.x and SPITFIRE BBSs. If you cannot locate a program to perform this task, please contact Carl Sagerquist through the contacts listed above. Explain in detail how your BBS operates regarding the upgrade of user security levels, send the appropriate files (drop file, database files if necessary) and I'll get to work on it. There's no extra charges for this work, as many other sysops will then be able to use this product, increasing its marketability! Thank you for supporting VERIFY!! OVERVIEW -------- VERIFY! was written by request from a MAXIHOST BBS sysop who had some difficulty with some rude callers. These people would call under fake names and leave foul messages, upload rude material, etc. This sysop needed a program that would validate each caller prior to authorizing access. VERIFY! performs this duty by returning the call to the user, and comparing the name and password left behind with the name and password typed in after the call back. If verified, VERIFY!.LST keeps a ready reference of verified callers and their phone numbers, and is read by VERIFY! to avoid double verification, and duplicate phone numbers. After verification, the callers are accountable, and they know it! OPERATION --------- VERIFY! performs a series of steps to complete the task of on-line verification. The caller is given the opportunity to stop the process and exit the program, if desired. 1 - Caller is asked if he wants to be verified for access. 2 - The caller's name is compared to the names in the file VERIFY!.LST. If found, the caller is advised that verification has already been successful, and the program exits. 3 - Instructions are issued, then caller is asked if he wants to proceed. 4 - The caller's information (name, phone number, password) is placed on the screen from the BBS's drop file if available. If the information is not correct, the caller may correct it. If a different name is typed in, it will be reflected in the file VERIFY!.LST. 5 - Phone number is checked against all others within the file VERIFY!.LST. If the number provided by the caller is already in this list, the verification process stops and the caller is notified to leave a message to the sysop regarding his access. It could be that this caller is a previous verified user under a fake name! You might want to place other BBS phone numbers here, so a prankster won't have your BBS hook to another BBS! 6a- REGISTERED VERSION ONLY: Phone number is checked against the local prefixes, non-local prefixes, and area codes from SETUP.EXE. If the area code and/or prefix is not found, the call is not placed, and the caller is notified to leave a message to the sysop, regarding BBS access. This controls the sysop phone bill. 6b- UNREGISTERED VERSION: All requests for call back verify will be granted. The sysop phone bill will reflect any long distance call backs! It is recommended that you register this program promptly, as your increased phone bill will quickly exceed the registration price if you have a lot of long distance callers!!! 7 - BOTH REGISTERED and UNREGISTERED: Certain calls can be very expensive. Calls to a 976 prefix or area code 900 can be extremely costly. From SETUP.EXE, define the unauthorized area codes or prefixes and these numbers will not be dialed. The first prankster that gets upset through your use of this program might try to get even by typing in a 976 number, or 911! VERIFY!.EXE is one step ahead! 8 - REGISTERED VERSION ONLY: If Local Call Back Times are defined (SETUP.EXE, Other window), the local call back is screened. If this function is not disabled, (with 0 - 0), VERIFY! will either return the call, or advise the caller of the normal times that his call back can be placed. 9 - REGISTERED VERSION ONLY: If the call back will be a long distance number, and it checks out OK, the time is checked to be within the two times defined from SETUP.EXE. If this function is not disabled, (with 0 - 0), VERIFY! will either return the call, or advise the caller of the normal times that his call back can be placed. 10 - Modem hangs up. 11 - The caller's phone number is dialed. If another caller tries to call the BBS while the call back is in progress, VERIFY! will recognize this call and take the phone line "off hook" for about 2 seconds, then hang up again. The current process of resetting the modem and calling is started over. 12 - When the caller answers, he will be given the opportunity to type in his name and password again. VERIFY! compares this data to the data left behind before the call back. If it matches, the caller is advised that he is verified. 13 - If verification is successful, caller is thanked for proper verification. If the call was local, the caller is returned to the BBS. If the call was long distance, a message is issued stating that this is a toll call, and that access will be granted on next call. The phone line is then disconnected. Without this feature, the BBS would continue at the sysop's expense. If the call back was long distance, it could become extremely costly to the sysop. The UNREGISTERED version WILL disconnect on toll calls. Also, with the /H:YES command line switch, after all completed verifications, the line will be disconnected. 14 - The log file is created or appended with information regarding the caller's actions. The data includes the caller's name from the BBS drop file, the name typed in if corrected, and phone number (if he got that far), the date and time, and the result of VERIFY!. Results include statements like: "***** VERIFIED! Local *****", "Carrier lost", "Decided not to be verified", etc. The log file is either VERIFY!.LOG, or the file name defined on the command line with the /L: switch. 15 - On exit of VERIFY!, ERRORLEVELs are returned to the calling batch file. It is then your responsibility to invoke a BBS utility program to adjust your caller's BBS security level or perform what ever duty you need. Even if nothing is done to the BBS at all, you will have the new name in VERIFY!.LST with the correct phone number. If you don't understand DOS ERRORLEVELs, you'll need to review your DOS manual. AREA CODES AND PREFIXES FROM SETUP.EXE -------------------------------------- If VERIFY! calls back the user, how can you keep a tab on your phone bill? This was a major consideration for this program. There are 7 different types of number windows in SETUP.EXE: 1 - Local Area Code for the BBS This is the local area code at the location where the BBS is run. 2 - Unauthorized Numbers If the caller's AREA CODE or PREFIX matches any three digit number on this line, then the call is not placed. This protects you from those very expensive 976 numbers and area code 900 numbers. This function is operational whether registered or not with one exception: Only the first three (three digit) numbers are active prior to registration. Be sure that the first three numbers on this line are "911 900 976". After registration, the entire line is active. Then, other numbers like "411 611" should be added, with any others you may feel necessary. 3 - LOCAL Prefixes If the caller's area code matches the Local Area Code for the BBS, then these numbers is checked for a match. If the prefix is found, then the callback will be a local call, and the dial string will only contain the 7 digit local number. Defining the local prefixes allows you to screen out those toll calls that look like local calls. If this line contains the number 000, then ALL numbers within the area code will be called, just as they are before registration. For example: These numbers are in the window of Local Prefixes: 943 944 945 948 949 723 722 264 and the Local Area Code for the BBS is 805. (805) 723-6908 is the caller's number. The caller's area code 805 matches the BBS's area code, so the Local line is searched for the prefix 723. 723 is found, so the dialed number will be 7236908. If the prefix is not found, the next set of numbers labeled "Authorized toll prefixes within the local area code" is checked. 4 - EXTRA LOCAL Prefixes If the caller's area code doesn't match the BBS's locall area code, then the "Extra Local" numbers are checked. In some areas of the country, a local call may be placed to a neighboring area code. These numbers are reached without dialing the area code. (See Metro Numbers below, if the area code must be dialed to place the call). In the "Extra Local Definitions" window of SETUP.EXE, you may define 3 area codes that are local calls. Within each area code, only certain prefixes are actually local to your phone. If all prefixes in this area code are local calls, place the wild card "000" in the prefix area and all prefixes are acceptable. Define the area code, then the prefixes that are local to your BBS. 7 didgets will be dialed if the caller's number matches a definition here. Since this is actually a local call at no charge to the sysop, the caller is not disconnected after verification. 5 - Metro Numbers If the caller's number isn't found within the local, extra local or toll numbers, the metro numbers are checked. Metro numbers are defined as local calls to another area code. There may be up to 9 metro area codes defined. The caller's area code is compared to these area codes. If there's a match, the caller's prefix is compared with the set of prefixes attached to the metro area code. The wildcard "000" may ne placed in the prefix area, and all the prefixes in that area code are acceptable. If there's a match (area code and prefix), the number is accepted as a metro number. The number is dialed with the area code, prefixed with a '1' if necessary. Since this is actually a local call at no charge to the sysop, the caller is not disconnected after verification. 6 - Authorized TOLL prefixes within the local area code If the caller's area code matches the Local Area Code for the BBS, and the caller's prefix is NOT found among the Local Prefixes, then this group of numbers is checked for the caller's prefix. If the prefix is found, then the callback will be an authorized toll call within the local area code. The dial string will only contain the 7 digit number. If this line contained the number 000, then ALL numbers within the area code will be called, just as they are before registration. For example: These numbers are on the line of Authorized toll prefixes...: 724 942 The search in 3 above was unsuccessful, so this line is searched for the prefix. (805) 942-0889 is the caller's number. The line is searched for the prefix 942. 942 is found, so the dialed number will be 9420889. If the prefix is not found, then the call back is not within the local area code. This allows you to designate the toll calls within your local area code you will allow to be called. Depending on your entry from SETUP.EXE, the number dialed here may or may not begin with a '1'. The number in this example will either be 9420889 or 19420889. 7 - Authorized long distance area codes If the caller's area code does not match the BBS's, the prefix checks are skipped, and this group of numbers is searched for the area code. If it is found, the number is called. If the number 000 is in this line, then ALL long distance calls will be placed, just as they are before registration. For example: These numbers are on the line of Authorized long distance area codes: 602 818 213 (602) 555-1212 is the caller's number. 602 is found, but the number is incomplete. First, the number 1 is appended to the dial string, then the full number, resulting in the dial string being 16025551212. If the area code is still not found, then the call is not placed. SYSOP HAS FULL CONTROL OF WHAT NUMBERS MAY BE CALLED! (REGISTERED VERSION ONLY!!!!!) NOTE: If the number called is a toll call (inside or outside the local area code), the line will hang up (be disconnected) after verification. This controls the sysop phone bill. Caller is advised that access is authorized on next call. REDIALS ------- VERIFY! can reattempt the phone call if the first attempt does not work. Often, an unsuspecting family member will pickup the phone on VERIFY!'s call back and break the modem connection. Sometimes, a caller is confused and just needs to try it more than once. Designate the amount of redial attempts through SETUP.EXE, Other window. When the modem disconnects and prepares for the call back, its possible for other BBS callers to try to log on. VERIFY!.EXE will intercept this incomming call. VERIFY!.EXE will take the phone line "off hook" for aprox. 2 seconds, then hang up. The current call back attempt is then restarted. This does not constitute one of the call back attempts defined through SETUP.EXE. If call back attempt number 1 is interrupted with an incomming call, then call back attempt number 1 is reattempted until the modem finds a dial tone and actually dials out. If this dialing is unsuccessful, then call back attempt number 2 is started. REATTEMPTS ---------- After call back, VERIFY! can also allow the caller to reattempt entering his/her name and password. The reattempts are defined with the redials. If redials are set to 2, and the caller spells his name wrong (don't laugh, there's many levels of brain power out there), the caller may reattempt 2 more times, totalling 3. CALL BACK HOURS --------------- Some sadistic callers might try to make your system call back other people they know (and dislike) by making VERIFY! call their number at 2:00 am! Thats why Local Call Back Times may be defined. If the call back is denied, the files LCL_TIME.ASC or LCL_TIME.ANS will be displayed before program exit. Most long distance carriers (phone companies) offer reduced rates within certain times. You can define your call back time for long distance calls to be within these times. These times are defined in SETUP.EXE, Other window. The numbers to be placed are the hours from the 24 hour clock. 1:00 pm is 13, 12:00 am is 24, etc. Hours only, no minutes. Example: 21 6 is for performing long distance call backs between 9:00 pm and 6:00 am. If you do not require screening your call back times, place the number 0 (zero) for both start and end times: 0 0 to disable this function, allowing call back at any time. OUTPUT ASCII/ANSI FILES ----------------------- The output files previously listed, are displayed during the operation of VERIFY!. They are named to give an idea of its objective: INSTRUCT.ANS is the ANSI color file that instructs the caller how to be verified, SUCCESS.ASC is the non-color file thats displayed on successful verification, etc. They may be edited to your liking. Do not include any more than one blank line after all the text in these files, or correct output may be compromised. The same is true if you exceed 23 lines, as none of the files will pause with a full screen. Any screen clearing in ANSI mode must be included in the .ANS file. VERIFY! does not automatically perform this duty. VERIFY!'s output may be personalized by placing the caller's name into the files! Place the '' character (from the <CTRL> E) and it will be replaced with the caller's first name. Place the '' (from the <CTRL> F) and it will be replaced with the caller's last name. Be sure to leave room on the line for these characters to expand to names, or the line might get cut in half. For example: Hello, . Would you like to be call back verified for a higher access level? Will be transmitted looking like this: Hello, Carl Sagerquist. Would you like to be call back verified for a higher ac cess level? Obviously, not desirable appearance. Remember to leave room for the names to be inserted to the line. CARRIER MONITOR --------------- VERIFY! monitors the Carrier Detect. If a caller hangs up, or gets disconnected, VERIFY! will exit clean and return to the BBS. The BBS will then reset and await the next call. You can test this feature by typing the ~ character at any prompt. TIME LIMIT ---------- The caller has 120 seconds to complete each entry, or carrier is dropped and the program exits. That way, if your caller's computer freezes, you aren't stuck on line! This feature was added to disallow remote's control of the carrier. Without this feature, the call back could last as long as the remote caller would allow. If the call back was long distance, your phone bill could sink you. You can test this feature by typing the (^A) character at any prompt or waiting 120 seconds without input. NONSTANDARD IRQ --------------- Nonstandard IRQs are not a problem. VERIFY!.EXE is written to operate on the standard IRQ's (Com1 and Com3;IRQ4, Com2 and Com4;IRQ3). If your system is set up operating on a different IRQ channel, edit the text file NSTD.IRQ. Its simply a listing of the NODE and its IRQ. Please note that the NODE isn't necessarily the COM PORT! The text file syntax is simple: NODE#;IRQ#. NODE1;IRQ5 NODE2;IRQ6 NODE3;IRQ7 NODE4;IRQ12 The syntax must start on the first character of the line, no spaces. If NODE1 uses COM2;IRQ6, then use: NODE1;IRQ6 If the first character of the line is an asterisk (*), the line is a comment and ignored. The file NSTD.IRQ need not exist at all. The next requirement is for the NODE to be defined. Usually, this takes place within the BBS DROP FILE, but some (like CHAIN.TXT) do not define the node. The command line switch /NODE:# is then used. BBS ADJUSTMENTS --------------- VERIFY! does no adjustments to your BBS itself. You, as sysop, are responsible to code your calling batch file appropriately to effect change. The returned ERRORLEVELs from VERIFY! will allow you to to do this. MEGAHOST includes the file MEGA_API.EXE to adjust a caller's security level while the caller is on line. 4-TRIBBS.ZIP, included with this package, contains TRISEC.EXE which will adjust the caller's security level and remaining time while the caller is on line for a TriBBS BBS. The security level change program TRISEC.EXE is part of the SME TriBBS Utility Package, included here for your convenience, and works with TriBBS v10.x and above. A version for TriBBS v5.x is available on the SME Support BBS on request. 4-WC40.ZIP, included with this package, contains W!4SEC.EXE which will adjust the caller's security level and remaining time while the caller is on line for a WILDCAT v4.0 BBS. A version of this program for use with WILDCAT v3.x is available on the SME Support BBS. 4SPTFIRE.ZIP, included with this package, contains SFSEC.EXE which will adjust the caller's security level and remaining time while the caller is on line for a SPITFIRE BBS. 4-LORA.ZIP, included with this package, contains LORASEC.EXE which changes the caller's security level while the caller is online. Other BBSs can be supported, too. If you need a utility to make the adjustments, send a message to the sysop on The SME Support BBS at (805) 723-6908 or via the internet at zs@qnet.com, and I'll get to work on it! ERRORLEVELS ----------- VERIFY! will return different errorlevels for further processing by the calling batch file: ERRORLEVEL 0 means the caller is verified, and all data matched. Call back was LOCAL. ERRORLEVEL 1 means the caller is verified, and all data matched. Call back was LONG DISTANCE. ERRORLEVEL 2 means the caller has already been verified. ERRORLEVEL 3 means the caller reentered the wrong data on callback. Caller not verified. ERRORLEVEL 4 means no modem on callback. Caller not verified. ERRORLEVEL 5 means the caller's phone number duplicates another verified caller's phone number. Could be a bogus call. ERRORLEVEL 6 means the callback phone number is within the local area code, and is not authorized. ERRORLEVEL 7 means long distance callback not within time envelope. ERRORLEVEL 8 means the caller typed an unauthorized number like 911. ERRORLEVEL 9 means the callback phone number contained one of the defined unauthorized area codes/prefixes. ERRORLEVEL 10 means the caller decided not to be verified. ERRORLEVEL 11 means the callback phone number is long distance and is not authorized. ERRORLEVEL 20 means unsupported comm port. ERRORLEVEL 30 means the remote input time limit (120 seconds) exceeded. ERRORLEVEL 40 means memory allocation error. ERRORLEVEL 50 means file open error. ERRORLEVEL 60 means file read error. ERRORLEVEL 70 means file write error. ERRORLEVEL 80 means file lock error. ERRORLEVEL 90 means file unlock error. ERRORLEVEL 100 means carrier lost. ERRORLEVEL 110 means user BREAK received. ERRORLEVEL 120 means modem framing error. ERRORLEVEL 130 means modem parity error. ERRORLEVEL 140 means modem buffer overrun error. SAMPLE BATCH FILE FOR TRIBBS ---------------------------- Note: The batch file in this example would be named VERIFY! (no extention) and the entry in DOORS.MNU should be: T,Call Back Verification,VERIFY!,10 @echo off CLS C: CD\VERIFY! VERIFY! /B:TRIBBS /D:C:\TRIBBS /L:C:\TRIBBS\NWORK\CALLERS.LOG IF ERRORLEVEL 1 IF NOT ERRORLEVEL 2 goto ADJUST IF ERRORLEVEL 0 IF NOT ERRORLEVEL 1 goto ADJUST GOTO END :ADJUST CD C:\TRIBBS\SME_UTLS TRISEC /S:25 /T+:30 :END CD\TRIBBS BOARD PRANKSTER CONTROL ----------------- If everyone was honest and respectful, there would be no need for this program. Some people spray paint on walls. Some people throw rocks through windows. The same mentality will call a BBS incognito and raise havoc with the sysop and his users through foul messages, uploaded dirty files, etc. When a prankster is caught by this program, he may feel a desire to get even. This program was written with this prankster mentality in mind. The controlling features are: 1 - 60 second timer for user input. A caller cannot hook you to his computer indefinitely, thus controlling your phone bill (long distance/toll calls). 2 - No duplicate phone numbers on automatic verify. - A new caller with the same phone number of a previously verified caller could be the same person under a different name! - A prankster might try to make your BBS hook up to another BBS! Place ALL possible BBS numbers into the file VERIFY!.LST, and this will not happen! 3 - Numbers defined as UNAUTHORIZED NUMBERS (through SETUP.EXE) are screened out. A prankster might try to make your computer call a 976 or area code 900 number. Also, if the call back was 911-####, the 911 would connect you to the emergency dispatch in your city! These numbers should be placed in the window labeled: UNAUTHORIZED NUMBERS through SETUP.EXE. The first three (three digit) numbers of this line are operational prior to registration. 4 - Long distance numbers are not called unless the area code is designated. (REGISTERED VERSION ONLY). Lets face it, even honest people will use this program without compensation to the programmer if every feature was operational! Use caution, though, ALL long distance calls are placed until VERIFY! is registered, and your phone bill will quickly exceed the registration fee requested. 5 - Log file appended after caller is done. The result of the caller's actions are placed in the file VERIFY!.LOG with the date and time, or the log file defined on the command line. 6 - Local call back time may be defined. This way, a caller cannot make your system call his neighbor at 2:00 am. Although the caller may still pull this stunt, if your call back time window is 9:00 am through 8:00 pm, no one will loose any sleep over it. If you find a need for more techniques on handling pranksters, please make the suggestion via The S M E Support BBS at (805) 723-6908, or via internet e-mail at zs@qnet.com. KNOWN PROBLEMS -------------- During the disconnect of the modem and call back, ATZ (modem reset) is sent to the host modem. This could cause trouble with some BBSs if the default values set with ATZ do not match the initialization string of the BBS. To correct this, append your BBS's initialization string with &W. The &W should be the last item before the CR at the end of the string. What this does is write the string to the modem's non- volatile memory. ATZ then resets the modem with these values. Then, leave the initialization string in VERIFY!'s SETUP.EXE blank, or place ATZ as the initialization string. For a modem that has no nonvolatile memory, use this initialization string to make the proper settings. CREDITS ------- Many thanks to Tim Gimber of Phoenix, AZ., who suggested this program, directed its features, and tested its operation. Many thanks to David Swift of Waldorf, MD., for advising me of the fatal error fixed with revision 2.2. This problem didn't occur on my modem, and I still don't understand why. VERIFY! is now compatible with many more modems. Many thanks to Kent Craig of Vincennes, IN., for advising me of the methods used by the Indiana phone system: Toll Local numbers there require the number to begin with a '1'. Now, through SETUP.EXE, the sysop may choose to prefix a Toll Local number with a '1'. Verify! is now compatible with more phone systems. Thanks to Raymond Swigirt of Baltimore, MD., for requesting room necessary to handle all 281 of the local prefixes available in Baltimore. The suggestion motivated me to revise the serial port routines, command line switches, and shared file access for multi- tasking environments. Thanks to James Mann of Littlerock, CA. for requesting the TRIBBS support programs and testing them online. Thanks to Robert Massman of Dallas TX. for his guidance on VERIFY!'s support of TRIBBS v4.2, and for testing VERIFY!.EXE revision 3.0's support for "Metro Numbers" prior to release. Thanks to Rick Bretz of Columbus, OH. for his guidance in fixing the error found when VERIFY! disconnects on a long distance unsuccessful verify, and for requesting the feature that intercepts a BBS call during the call back process. Thanks for the effort! Thanks to Marc Neveux of Thousand Oaks, CA., for identifying the error when a caller with a one word name tries to be verified. Thanks to Debbie Engwiller of Rosamond, CA. for requesting the user editable ASCII/ANSI output files for customizing VERIFY!'s output. Thanks (again) to Robert Massman of Dallas TX. for his continued persistance to keep VERIFY!.EXE up to date with "Ma Bell" in the Dallas, TX area with enough Local numbers and Metro numbers. Thanks to Gloria Short of the BRAIN STORM LEARNING BBS, HOUSTON, TX for the help received to make VERIFY! operational with the RoboBoard BBS. Thanks to Doug Torneden of Irving, TX for the suggestion to have VERIFY!.EXE echo all modem commands and result messages to the screen. Internal modem BBSs can now see the modem processing. Thanks again to Debbie Engwiller of Rosamond, CA. for requesting the /REQUIRED: command line switch allowing the sysop to force the caller to perform the call back verify, or disconnect. Thanks to John and Helen Knopf of Collierville, TN and Jackie Hubbard of Olive Branch, MS for requesting the "Extra Local Definitions", allowing a 7 didget number to call a neighboring area code. Thanks to David Chen of Richmond, CA for requesting the caller's name, phone number and password be taken from the BBS drop file. Thanks to Joe Stevens of Raleigh, NC, for requesting to control the hangup function. Depending on the /H: command line switch, the hangup function may or may not be invoked. Thanks to Jeff Cruser of Houston, TX for requesting the definition of ERRORLEVEL 11. Now if a long distance call is not allowed, the batch file may branch to another part and perform a special function for this caller like upgrade the security level. Thanks to Bob Riddell of Belleville, IL for his input regarding Remote Access's use of DORINFO1.DEF regardless of the node in use. Thanks VERY MUCH!!! to Rick Bretz of Colombus, OH, again! for the persistance with the fatal error in v3.5, fixed in v3.5a. Thanks to Guy Islip of Duncan, British Columbia, Canada, for the suggestion to control the local call back times. Thanks to Ernest Nachtigall of Brampton, Ontario, Canada for his fine work describing the operation needed in Brampton, and for testing the finished product, v3.6. Thanks to Marco Maccaferri, author of LoraBBS for his assistance with my coding for LIRAINFO.Txx and password encryption. Thanks to Robert Butler of Killeen, TX, (member of the LoraBBS team) for his testing and input on a LoraBBS system including the security level upgrade program. Thanks (again) to Jeff Cruser of Houston, TX and Keith Heitmann of Portage, IN for their persistance in communicating the error found when the list file VERIFY!.LST became too large for the function written to read it, resulting in version 3.9. DISCLAIMER ---------- This program is distributed as is. No warranty, either expressed or implied is offered and the programmer is not responsible for any damages or expenses that may occur through the use of this program. The user shall determine its suitability. Please communicate any difficulties with the programmer through the BBS at (805) 723-6908. Any errors reported will be handled as a top priority. History ------- Version 3.9 - 02/11/96 - Fixed memory overflow problem caused when the size of the file VERIFY!.LST became larger than the buffer allocated for it. Happy Birthday, Carl! Version 3.8 - 01/19/96 - Switch VERIFY!.EXE's compiler from POWER C (Mix Software) to Borland C/C++. - Error in online operation of LoraBBS fixed. - Exception handling code overhauled. - Interrupt driver altered, now responds correctly to the USER BREAK signal, and other possible modem errors. - ERRORLEVELs at and above 20 changed. - File locking for a multitasking environment used before writing to the log and list files. SHARE.EXE must be loaded. Version 3.7 - 12/26/95 - Added LORABBS to the supported BBS list. Area codes no longer checked for the middle didget to be a 0 or 1. This used to be the case in the US. Version 3.6 - 05/12/95 - "000" wild card may now be used in the Metro Numbers. - Now, if you need to dial the full long distance number "1-AAA-xxx-xxxx" within your own local area code, just add your local area code to the Area Codes (LD) window, rather than "000 AAA" (where "AAA" is your local area code: "000 805"). Version 3.5b - 04/21/95 - TRISEC.EXE (in 4-TRIBBS.ZIP) revised, and VERIFY!.DOC slightly modified to reflect TRISEC's changes in the batch file suggestion. Added Local Call Back Time Window (SETUP.EXE, Other window). Call back time for local calls may now be defined. NOT_NOW.ASC/ANS is obsolete. It is replaced with LD_TIME.ASC/ANS since now local calls can also be "window'ed". Local calls that are denied will display LCL_TIME.ASC/ANS. If F10 is hit at the local keyboard, (to exit the program simulating successful callback), the entry to VERIFY!.LST is now correctly placed. Version 3.5a - 03/20/95 - Repaired error in the function that checks the file VERIFY!.LST for the current caller. A buffer was too small, and when I revised the output to the .LST file to include the original name and any possible changed name, the buffer overflowed. FIXED!!! Version 3.5 - 03/15/95 - Registration routine revised. Previously registered sysops must call for their new number, supplied free of charge. - ERRORLEVEL 6 revised, ERRORLEVEL 11 added allowing you to check for unauthorized long distance numbers. Some sysops want to raise these caller's security anyway. - Nonstandard IRQ's now handled. - The caller's name, password and phone number is now extracted from the BBS's drop file, if the data is there. Both names, the one from the drop file and the newly typed name are printed to the log and list files. - The caller may reenter the name, phone number and password if its incorrect. - Callback Attempts (as defined in SETUP.EXE) now includes retries. The caller may retry to correctly enter his name and password on call back. - The log file now logs the caller's real name in case the caller types in a name that does not match his own. The .LST file contains both names. - Added /H: command line switch to control the hangup function. - Added /REQUIRED: command line switch to control a forced verify. - Added REQUIRED.ASC/ANS if the /REQUIRED:YES command line switch is used. - Added "Extra Local Definitions" for those geographical areas that allow for dialing a 7 didget number (local call) into a neighboring area code. - Adjusted operation with Remote Access to look for DORINFO1.DEF regardless of the node in use. Version 3.4 - 02/01/94 - Added the SABOTAGE.ASC/ANS screen when a caller types in an area code or prefix that matches one of the defined UNAUTHORIZED numbers. - Added 15 more lines of Local Prefixes in a third Local Prefix window. - Tripled the amount of definable Metro Numbers through two more Metro Number windows. - Added support for RoboBoard BBS through DORINFO#.DEF. - Modem commands/results now echoed to the local screen. Version 3.3 - 12/19/93 - Revised output: Most output now comes from ASCII/ANSI files. The sysop may alter VERIFY!'s appearance. Version 3.2 - 11/21/93 - Modem interrupts cleared prior to exit removing erroneous error response. - RBBS# command line switch fixed. - Fixed problem in name comparison caused when a caller logs on with a one word name. - Added the command line switch RENEGADE# (/B:RENEGADE1) to support the Renegade BBS. Version 3.1a - 09/07/93 - Discovered error in support for AUNTIE BBS, in the opening of AUNTIE.SYS. Fixed. Version 3.1 - 09/06/93 - Added code to intercept an incomming call when the callback sequence has begun. - Removed command line switch TRIBBS_D since the support programs are written to work only with TRIBBS.SYS, not DOOR.SYS. - Command line switch TRIBBS_T altered to TRIBBS (/B:TRIBBS). - Removed command line switch RA for use with DOOR.SYS. RA now will only work with the more useful file DORINFOx.BBS. - Added AUNTIE BBS to supported list through command line switch /B:AUNTIE. - Added PROBOARD BBS to supported list through command line switch /B:PROBOARD# where the # is the node number. Version 3.0 - 08/15/93 - Support for Metro Numbers added. - If upgrading from v2.8 or 2.9, the file VERIFY!.DAT is automatically adjusted through FIX_DAT.EXE to ensure a clean operation should you forget to make the data adjustments through SETUP.EXE. New variables in VERIFY!.DAT are blank, waiting for later input. - Utilities for TRIBBS adjusted for use with TRIBBS v4.02. Previous release supported v3.3 only. - Added the command line switch VBBS (/B:VBBS) to support the Virtual BBS/NET, AKA VBBS. - PCBoard now supported through PCBOARD.SYS. - VERIFY!.LOG entries altered to conform to TRIBBS's log entry format. Should look good in all applications. Version 2.9 - 07/11/93 - Utilities created for security level adjustment on a TRIBBS BBS, through TRIBBS.SYS. - Fatal error found: If all data in the file VERIFY!.LST is removed, yet the zero length file still exists, the program would freeze. FIXED! Version 2.8 - 04/04/93 - Comm port routines overhauled. Now, all data transmitted and received is interrupt driven, and more thorough error checking is performed. - All file access is performed in share mode. Files are "locked" prior to writing which allows for a clean operation in a multi- tasking environment where a multi-line BBS might be operating VERIFY! simultaneously on more than one node. - Command line switches overhauled. - VERIFY! may now log its actions into the BBS's log file through the /L: command line switch. - Amount of definable local prefixes is now 510, double from v2.6. - MEGAHOST now supported through MEGAHST#.DEF rather than DOOR.SYS. - TRIBBS now supported through TRIBBS.SYS and DOOR.SYS. - WILDCAT! v3.0+ now supported through the new format of DOOR.SYS. Version 2.7 - ??/??/?? - Beta test only, not released to the public. Version 2.6 - 04/24/92 - Local Prefixes, Toll Local Prefixes, and L/D Area Codes are increased from 3 lines to 9 lines of 67 characters. - Toll Local call back number may be prefixed with a 1 if necessary. Use SETUP.EXE to make the adjustment. Version 2.5 - 04/08/92 - Added an option allowing the caller to quit. For example: "Are you ready to proceed? (Y/n)" is replaced with "Are you ready to proceed? (Y/n/q)" where 'Y' is default, and 'Q' exits the program. - SETUP.EXE adjusted. New features: - If data is changed, you are prompted to save. - <CTRL> Right Arrow moves the curser to the beginning of the next number in the "Numbers" window. - <CTRL> Left Arrow moves the curser to the beginning of the previous number in the "Numbers" window. - Up Arrow/Down arrow moves to different lines in the "Numbers" window. Version 2.4 - 01/01/92 - SETUP.EXE added to automate the setup operation. All data from SETUP.EXE is written to VERIFY!.DAT, which is now a binary structure file. - VERIFY!.NUM is no longer needed. - MAXIHOST no longer listed as supported since M-VERIFY v 1.09 is still available. Version 2.3 - 12/15/91 - Beta test version not released. Version 2.2 - 12/10/91 - Fatal error found with some modems (not mine) that would disrupt the comm port interrupts. Unnecessary code removed that set some modem parameters. Thanks, Dave! - More BBS's supported: PcBoard Remote Access Teleguard TGP WWIV Version 2.1 - 10/14/91 - Bug in toll/long distance call timer fixed. - When the toll/ld call is screened out, the current time is displayed before the message explaining the time window for toll calls. - Caller is now informed how many attempts will be made to call back and connect. Version 2.0 - 10/10/91 - Program renamed from M-VERIFY to VERIFY!. - Supports MAXIHOST, MEGAHOST, QBBS, RBBS, PCBoard, and WILDCAT. Syntax different while retaining the old method. - No adjustments to MAXIHOST or its assoc'd files anymore. - ERRORLEVELS returned. The sysop must make the appropriate adjustments to the BBS depending on the ERRORLEVEL returned. Version 1.09 - 11/29/91 - Modem parameters (BAUD, Parity, Stop bits, and Character length) are no longer set. This was causing trouble with some modems. Unfortunately, not mine. This may have been the culprit causing trouble with earlier versions. These parameters are set by the BBS anyway, so there's no harm in removing this code. Same code removed from version 2.1. Version 1.08 - 09/16/91 - Sorry about that, another bug got by me. Version 1.07 - 09/16/91 - Some code rewritten for efficiency and safety. No changes in operation from 1.06. Version 1.06 - 09/15/91 - Fixed FATAL ERROR in delay function that violated memory not its own which eventually caused system to crash. Version 1.05 - 08/09/91 - 'REDIALS = ' added to M-VERIFY.DAT to control the amount of attempts to recontact the caller. Version 1.04 - 08/07/91 - Long Distance call back time now definable, since most long distance carriers allow for cheaper rates at different times. - Removed the advertisement at beginning of output on registered version. Version 1.03 - 07/28/91 - Fixed bug in log file entry that says "**** VERIFIED (Long Distance) ****" when caller really "Already Verified". - Fixed bug that created M-VERIFY.LOG in the root directory if M-VERIFY.EXE was called without the proper command line parameters. Version 1.02 - 07/26/91 - Registration required. Without the reg #, all call backs are placed regardless of the area code or resultant phone charges. Call back screening enabled with registration. - M-VERIFY now screens OUT certain area codes or prefixes, like 976 and 900, while author- ized numbers are screened IN. (Sysop can define these numbers in M-VERIFY.NUM). - M-VERIFY now checks for toll calls within the local area code. Caller is disconnected after verification if callback is a toll call. - ERRORLEVELs 1 through 5 become 2 through 6, and ERRORLEVEL 1 redefined: ERRORLEVEL 1 returned if caller is verified and call back is long distance. ERRORLEVEL 0 if call back is local. Version 1.01 - 07/21/91 - Delay added after "Returning Your Call" sent, as it was being cut off by hanging up too quick. - Bug in hangup routine: After verification, if call back was long distance, dropping DTR wasn't enough to disconnect. Hangup routine fixed. Version 1.0 - 07/19/91 - Initial release. Version 0.2 - 07/14/91 - Beta test released to requesting official, not to be released to public. Partially completed. Version 0.1 - 07/09/91 - Beta test released to requesting official, not to be released to public. Partially completed.